External data interface in a computer architecture for broadband networks

ABSTRACT

A system configuration includes a processing element (PE), an input/output (I/O) interface device and a shared memory. The PE further includes at least one processing unit (PU) and one, or more, attached processing units (APUs). At least one of the APUs performs an I/O function by reading data from, and writing data to, an external device coupled to the I/O interface device. Data is exchanged between the APU and the I/O interface device via the shared memory using a data level synchronization mechanism.

CROSS-REFERENCE TO RELATED APPLICATIONS

This is a continuation-in-part of the following copending, commonly assigned, U.S. Patent applications: “Computer Architecture and Software Cells for Broadband Networks,” application Ser. No. 09/816,004, filed Mar. 22, 2001; “System and Method for Data Synchronization for a Computer Architecture for Broadband Networks,” application Ser. No. 09/815,554, filed Mar. 22, 2001 now U.S. Pat. No. 6,826,662; “Memory Protection System and Method for Computer Architecture for Broadband Networks,” application Ser. No. 09/816,020, filed Mar. 22, 2001 now U.S. Pat. No. 6,526,491; “Resource Dedication System and Method for a Computer Architecture for Broadband Networks,” application Ser. No. 09/815,558, filed Mar. 22, 2001 now U.S. Pat. No. 6,809,734; and “Processing Modules for Computer Architecture for Broadband Networks,” application Ser. No. 09/816,752, filed Mar. 22, 2001 now U.S. Pat. No. 7,093,104; all of which are incorporated by reference herein.

BACKGROUND OF THE INVENTION

The present invention relates to an architecture for computer processors and computer networks and, in particular, to an architecture for computer processors and computer networks in a broadband environment.

The computers and computing devices of current computer networks, e.g., local area networks (LANs) used in office networks and global networks such as the Internet, were designed principally for stand-alone computing. The sharing of data and application programs (“applications”) over a computer network was not a principal design goal of these computers and computing devices. These computers and computing devices also typically were designed using a wide assortment of different processors made by a variety of different manufacturers, e.g., Motorola, Intel, Texas Instruments, Sony and others. Each of these processors has its own particular instruction set and instruction set architecture (ISA), i.e., its own particular set of assembly language instructions and structure for the principal computational units and memory units for performing these instructions. A programmer is required to understand, therefore, each processor's instruction set and ISA to write applications for these processors. This heterogeneous combination of computers and computing devices on today's computer networks complicates the processing and sharing of data and applications. Multiple versions of the same application often are required, moreover, to accommodate this heterogeneous environment.

The types of computers and computing devices connected to global networks, particularly the Internet, are extensive. In addition to personal computers (PCs) and servers, these computing devices include cellular telephones, mobile computers, personal digital assistants (PDAs), set top boxes, digital televisions and many others. The sharing of data and applications among this assortment of computers and computing devices presents substantial problems.

A number of techniques have been employed in an attempt to overcome these problems. These techniques include, among others, sophisticated interfaces and complicated programming techniques. These solutions often require substantial increases in processing power to implement. They also often result in a substantial increase in the time required to process applications and to transmit data over networks.

Data typically are transmitted over the Internet separately from the corresponding applications. This approach avoids the necessity of sending the application with each set of transmitted data corresponding to the application. While this approach minimizes the amount of bandwidth needed, it also often causes frustration among users. The correct application, or the most current application, for the transmitted data may not be available on the client's computer. This approach also requires the writing of a multiplicity of versions of each application for the multiplicity of different ISAs and instruction sets employed by the processors on the network.

The Java model attempts to solve this problem. This model employs a small application (“applet”) complying with a strict security protocol. Applets are sent from a server computer over the network to be run by a client computer (“client”). To avoid having to send different versions of the same applet to clients employing different ISAs, all Java applets are run on a client's Java virtual machine. The Java virtual machine is software emulating a computer having a Java ISA and Java instruction set. This software, however, runs on the client's ISA and the client's instruction set. A version of the Java virtual machine is provided for each different ISA and instruction set of the clients. A multiplicity of different versions of each applet, therefore, is not required. Each client downloads only the correct Java virtual machine for its particular ISA and instruction set to run all Java applets.

Although providing a solution to the problem of having to write different versions of an application for each different ISA and instruction set, the Java processing model requires an additional layer of software on the client's computer. This additional layer of software significantly degrades a processor's processing speed. This decrease in speed is particularly significant for real-time, multimedia applications. A downloaded Java applet also may contain viruses, processing malfunctions, etc. These viruses and malfunctions can corrupt a client's database and cause other damage. Although a security protocol employed in the Java model attempts to overcome this problem by implementing a software “sandbox,” i.e., a space in the client's memory beyond which the Java applet cannot write data, this software-driven security model is often insecure in its implementation and requires even more processing.

Real-time, multimedia, network applications are becoming increasingly important. These network applications require extremely fast processing speeds. Many thousands of megabits of data per second may be needed in the future for such applications. The current architecture of networks, and particularly that of the Internet, and the programming model presently embodied in, e.g., the Java model, make reaching such processing speeds extremely difficult.

Therefore, a new computer architecture, a new architecture for computer networks and a new programming model are required. This new architecture and programming model should overcome the problems of sharing data and applications among the various members of a network without imposing added computational burdens. This new computer architecture and programming model also should overcome the security problems inherent in sharing applications and data among the members of a network.

SUMMARY OF THE INVENTION

A computer architecture for high speed processing over broadband networks is provided. In particular, and accordance with the invention, a system comprises an interface device for communicating data and a memory for storing the data, wherein the memory comprises at least one memory location and status information associated therewith, wherein the status information comprises a first field and an address field and wherein when a value of the first field equals a first value, and a value of the address field equals a second value, a subsequent write of the data to the associated memory location causes the data stored therein to be written to an address as represented by the address field value.

In an embodiment of the invention, a system configuration comprises a processing element (PE), an input/output (I/O) interface device and a shared memory. The PE further comprises at least one processing unit (PU) and one, or more, attached processing units (APUs). At least one of the APUs performs an I/O function by reading data from, and writing data to, an external device coupled to the I/O interface device. Data is exchanged between the APU and the I/O interface device, via the shared memory, using a data level synchronization mechanism. In particular, the shared memory comprises at least one status information location associated with at least one memory location for storing the data, wherein the status information location comprises a first field and an address field and wherein when a value of the first field equals a first value, and a value of the address field equals a second value, a subsequent write of the data to the associated memory location causes the data stored therein to be written to an address as represented by the address field value.

DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates the overall architecture of a computer network in accordance with the present invention.

FIG. 2 is a diagram illustrating the structure of a processor element (PE) in accordance with the present invention.

FIG. 3 is a diagram illustrating the structure of a broadband engine (BE) in accordance with the present invention.

FIG. 4 is a diagram illustrating the structure of an attached processing unit (APU) in accordance with the present invention.

FIG. 5 is a diagram illustrating the structure of a processor element, visualizer (VS) and an optical interface in accordance with the present invention.

FIG. 6 is a diagram illustrating one combination of processor elements in accordance with the present invention.

FIG. 7 illustrates another combination of processor elements in accordance with the present invention.

FIG. 8 illustrates yet another combination of processor elements in accordance with the present invention.

FIG. 9 illustrates yet another combination of processor elements in accordance with the present invention.

FIG. 10 illustrates yet another combination of processor elements in accordance with the present invention.

FIG. 11A illustrates the integration of optical interfaces within a chip package in accordance with the present invention.

FIG. 11B is a diagram of one configuration of processors using the optical interfaces of FIG. 11A.

FIG. 11C is a diagram of another configuration of processors using the optical interfaces of FIG. 11A.

FIG. 12A illustrates the structure of a memory system in accordance with the present invention.

FIG. 12B illustrates the writing of data from a first broadband engine to a second broadband engine in accordance with the present invention.

FIG. 13 is a diagram of the structure of a shared memory for a processor element in accordance with the present invention.

FIG. 14A illustrates one structure for a bank of the memory shown in FIG. 13.

FIG. 14B illustrates another structure for a bank of the memory shown in FIG. 13.

FIG. 15 illustrates a structure for a direct memory access controller in accordance with the present invention.

FIG. 16 illustrates an alternative structure for a direct memory access controller in accordance with the present invention.

FIGS. 17A–17O illustrate the operation of data synchronization in accordance with the present invention.

FIG. 18 is a three-state memory diagram illustrating the various states of a memory location in accordance with the data synchronization scheme of the present invention.

FIG. 19 illustrates the structure of a key control table for a hardware sandbox in accordance with the present invention.

FIG. 20 illustrates a scheme for storing memory access keys for a hardware sandbox in accordance with the present invention.

FIG. 21 illustrates the structure of a memory access control table for a hardware sandbox in accordance with the present invention.

FIG. 22 is a flow diagram of the steps for accessing a memory sandbox using the key control table of FIG. 19 and the memory access control table of FIG. 21.

FIG. 23 illustrates the structure of a software cell in accordance with the present invention.

FIG. 24 is a flow diagram of the steps for issuing remote procedure calls to APUs in accordance with the present invention.

FIG. 25 illustrates the structure of a dedicated pipeline for processing streaming data in accordance with the present invention.

FIG. 26 is a flow diagram of the steps performed by the dedicated pipeline of FIG. 25 in the processing of streaming data in accordance with the present invention.

FIG. 27 illustrates an alternative structure for a dedicated pipeline for the processing of streaming data in accordance with the present invention.

FIG. 28 illustrates a scheme for an absolute timer for coordinating the parallel processing of applications and data by APUs in accordance with the present invention.

FIGS. 29–30 show illustrative embodiments for configurations using data level synchronization in accordance with the principles of the invention.

FIGS. 31–32 show illustrative flow charts for use in performing data level synchronization in accordance with the principles of the invention.

FIGS. 33–34 illustrate the use of data level synchronization between an APU and an external device.

FIG. 35 shows illustrative data level synchronization status information in accordance with the principles of the invention.

FIG. 36 shows another illustrative embodiment for a configuration using data level synchronization in accordance with the principles of the invention.

FIG. 37 shows an illustrative handshaking sequence.

FIG. 38 shows another illustrative embodiment for a configuration using data level synchronization in accordance with the principles of the invention.

FIG. 39 shows another illustrative embodiment for a configuration using data level synchronization in accordance with the principles of the invention.

FIG. 40 shows another illustrative flow chart for use in performing data level synchronization in accordance with the principles of the invention.

FIG. 41 offers another illustration of the use of data level synchronization between an APU and an external device.

FIG. 42 shows another illustrative embodiment for a configuration using data level synchronization in accordance with the principles of the invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The overall architecture for a computer system 101 in accordance with the present invention is shown in FIG. 1.

As illustrated in this figure, system 101 includes network 104 to which is connected a plurality of computers and computing devices. Network 104 can be a LAN, a global network, such as the Internet, or any other computer network.

The computers and computing devices connected to network 104 (the network's “members”) include, e.g., client computers 106, server computers 108, personal digital assistants (PDAs) 110, digital television (DTV) 112 and other wired or wireless computers and computing devices. The processors employed by the members of network 104 are constructed from the same common computing module. These processors also preferably all have the same ISA and perform processing in accordance with the same instruction set. The number of modules included within any particular processor depends upon the processing power required by that processor.

For example, since servers 108 of system 101 perform more processing of data and applications than clients 106, servers 108 contain more computing modules than clients 106. PDAs 110, on the other hand, perform the least amount of processing. PDAs 110, therefore, contain the smallest number of computing modules. DTV 112 performs a level of processing between that of clients 106 and servers 108. DTV 112, therefore, contains a number of computing modules between that of clients 106 and servers 108. As discussed below, each computing module contains a processing controller and a plurality of identical processing units for performing parallel processing of the data and applications transmitted over network 104.

This homogeneous configuration for system 101 facilitates adaptability, processing speed and processing efficiency. Because each member of system 101 performs processing using one or more (or some fraction) of the same computing module, the particular computer or computing device performing the actual processing of data and applications is unimportant. The processing of a particular application and data, moreover, can be shared among the network's members. By uniquely identifying the cells comprising the data and applications processed by system 101 throughout the system, the processing results can be transmitted to the computer or computing device requesting the processing regardless of where this processing occurred. Because the modules performing this processing have a common structure and employ a common ISA, the computational burdens of an added layer of software to achieve compatibility among the processors is avoided. This architecture and programming model facilitates the processing speed necessary to execute, e.g., real-time, multimedia applications.

To take further advantage of the processing speeds and efficiencies facilitated by system 101, the data and applications processed by this system are packaged into uniquely identified, uniformly formatted software cells 102. Each software cell 102 contains, or can contain, both applications and data. Each software cell also contains an ID to globally identify the cell throughout network 104 and system 101. This uniformity of structure for the software cells, and the software cells' unique identification throughout the network, facilitates the processing of applications and data on any computer or computing device of the network. For example, a client 106 may formulate a software cell 102 but, because of the limited processing capabilities of client 106, transmit this software cell to a server 108 for processing. Software cells can migrate, therefore, throughout network 104 for processing on the basis of the availability of processing resources on the network.

The homogeneous structure of processors and software cells of system 101 also avoids many of the problems of today's heterogeneous networks. For example, inefficient programming models which seek to permit processing of applications on any ISA using any instruction set, e.g., virtual machines such as the Java virtual machine, are avoided. System 101, therefore, can implement broadband processing far more effectively and efficiently than today's networks.

The basic processing module for all members of network 104 is the processor element (PE). FIG. 2 illustrates the structure of a PE. As shown in this figure, PE 201 comprises a processing unit (PU) 203, a direct memory access controller (DMAC) 205 and a plurality of attached processing units (APUs), namely, APU 207, APU 209, APU 211, APU 213, APU 215, APU 217, APU 219 and APU 221. A local PE bus 223 transmits data and applications among the APUs, DMAC 205 and PU 203. Local PE bus 223 can have, e.g., a conventional architecture or be implemented as a packet switch network. Implementation as a packet switch network, while requiring more hardware, increases available bandwidth.

PE 201 can be constructed using various methods for implementing digital logic. PE 201 preferably is constructed, however, as a single integrated circuit employing a complementary metal oxide semiconductor (CMOS) on a silicon substrate. Alternative materials for substrates include gallium arsinide, gallium aluminum arsinide and other so-called III-B compounds employing a wide variety of dopants. PE 201 also could be implemented using superconducting material, e.g., rapid single-flux-quantum (RSFQ) logic.

PE 201 is closely associated with a dynamic random access memory (DRAM) 225 through a high bandwidth memory connection 227. DRAM 225 functions as the main memory for PE 201. Although a DRAM 225 preferably is a dynamic random access memory, DRAM 225 could be implemented using other means, e.g., as a static random access memory (SRAM), a magnetic random access memory (MRAM), an optical memory or a holographic memory. DMAC 205 facilitates the transfer of data between DRAM 225 and the APUs and PU of PE 201. As further discussed below, DMAC 205 designates for each APU an exclusive area in DRAM 225 into which only the APU can write data and from which only the APU can read data. This exclusive area is designated a “sandbox.”

PU 203 can be, e.g., a standard processor capable of stand-alone processing of data and applications. In operation, PU 203 schedules and orchestrates the processing of data and applications by the APUs. The APUs preferably are single instruction, multiple data (SIMD) processors. Under the control of PU 203, the APUs perform the processing of these data and applications in a parallel and independent manner. DMAC 205 controls accesses by PU 203 and the APUs to the data and applications stored in the shared DRAM 225. Although PE 201 preferably includes eight APUs, a greater or lesser number of APUs can be employed in a PE depending upon the processing power required. The PU 203 and some or all of the APUs may have the same hardware structure and/or functionality. Individual processors may be configured as controlling or controlled processors, if necessary, by software. For instance, in FIG. 3, the PE 201 may include nine processors having the same architecture. One of the nine processors may be designated as a controlling processor (e.g., PU 203) and the remaining processors may be designated as controlled processors (e.g., APUs 207, 209, 211, 213, 215, 217, 219 and 221). Also, a number of PEs, such as PE 201, may be joined or packaged together to provide enhanced processing power.

For example, as shown in FIG. 3, four PEs may be packaged or joined together, e.g., within one or more chip packages, to form a single processor for a member of network 104. This configuration is designated a broadband engine (BE). As shown in FIG. 3, BE 301 contains four PEs, namely, PE 303, PE 305, PE 307 and PE 309. Communications among these PEs are over BE bus 311. Broad bandwidth memory connection 313 provides communication between shared DRAM 315 and these PEs. In lieu of BE bus 311, communications among the PEs of BE 301 can occur through DRAM 315 and this memory connection.

Input/output (I/O) interface 317 and external bus 319 provide communications between broadband engine 301 and the other members of network 104. Each PE of BE 301 performs processing of data and applications in a parallel and independent manner analogous to the parallel and independent processing of applications and data performed by the APUs of a PE.

FIG. 4 illustrates the structure of an APU. APU 402 includes local memory 406, registers 410, four floating point units 412 and four integer units 414. Again, however, depending upon the processing power required, a greater or lesser number of floating points units 512 and integer units 414 can be employed. In a preferred embodiment, local memory 406 contains 128 kilobytes of storage, and the capacity of registers 410 is 128×128 bits. Floating point units 412 preferably operate at a speed of 32 billion floating point operations per second (32 GFLOPS), and integer units 414 preferably operate at a speed of 32 billion operations per second (32 GOPS).

Local memory 402 is not a cache memory. Local memory 402 is preferably constructed as an SRAM. Cache coherency support for an APU is unnecessary. A PU may require cache coherency support for direct memory accesses initiated by the PU. Cache coherency support is not required, however, for direct memory accesses initiated by an APU or for accesses from and to external devices.

APU 402 further includes bus 404 for transmitting applications and data to and from the APU. In a preferred embodiment, this bus is 1,024 bits wide. APU 402 further includes internal busses 408, 420 and 418. In a preferred embodiment, bus 408 has a width of 256 bits and provides communications between local memory 406 and registers 410. Busses 420 and 418 provide communications between, respectively, registers 410 and floating point units 412, and registers 410 and integer units 414. In a preferred embodiment, the width of busses 418 and 420 from registers 410 to the floating point or integer units is 384 bits, and the width of busses 418 and 420 from the floating point or integer units to registers 410 is 128 bits. The larger width of these busses from registers 410 to the floating point or integer units than from these units to registers 410 accommodates the larger data flow from registers 410 during processing. A maximum of three words are needed for each calculation. The result of each calculation, however, normally is only one word.

FIGS. 5–10 further illustrate the modular structure of the processors of the members of network 104. For example, as shown in FIG. 5, a processor may comprise a single PE 502. As discussed above, this PE typically comprises a PU, DMAC and eight APUs. Each APU includes local storage (LS). On the other hand, a processor may comprise the structure of visualizer (VS) 505. As shown in FIG. 5, VS 505 comprises PU 512, DMAC 514 and four APUs, namely, APU 516, APU 518, APU 520 and APU 522. The space within the chip package normally occupied by the other four APUs of a PE is occupied in this case by pixel engine 508, image cache 510 and cathode ray tube controller (CRTC) 504. Depending upon the speed of communications required for PE 502 or VS 505, optical interface 506 also may be included on the chip package.

Using this standardized, modular structure, numerous other variations of processors can be constructed easily and efficiently. For example, the processor shown in FIG. 6 comprises two chip packages, namely, chip package 602 comprising a BE and chip package 604 comprising four VSs. Input/output (I/O) 606 provides an interface between the BE of chip package 602 and network 104. Bus 608 provides communications between chip package 602 and chip package 604. Input output processor (IOP) 610 controls the flow of data into and out of I/O 606. I/O 606 may be fabricated as an application specific integrated circuit (ASIC). The output from the VSs is video signal 612.

FIG. 7 illustrates a chip package for a BE 702 with two optical interfaces 704 and 706 for providing ultra high speed communications to the other members of network 104 (or other chip packages locally connected). BE 702 can function as, e.g., a server on network 104.

The chip package of FIG. 8 comprises two PEs 802 and 804 and two VSs 806 and 808. An I/O 810 provides an interface between the chip package and network 104. The output from the chip package is a video signal. This configuration may function as, e.g., a graphics work station.

FIG. 9 illustrates yet another configuration. This configuration contains one-half of the processing power of the configuration illustrated in FIG. 8. Instead of two PEs, one PE 902 is provided, and instead of two VSs, one VS 904 is provided. I/O 906 has one-half the bandwidth of the I/O illustrated in FIG. 8. Such a processor also may function, however, as a graphics work station.

A final configuration is shown in FIG. 10. This processor consists of only a single VS 1002 and an I/O 1004. This configuration may function as, e.g., a PDA.

FIG. 11A illustrates the integration of optical interfaces into a chip package of a processor of network 104. These optical interfaces convert optical signals to electrical signals and electrical signals to optical signals and can be constructed from a variety of materials including, e.g., gallium arsinide, aluminum gallium arsinide, germanium and other elements or compounds. As shown in this figure, optical interfaces 1104 and 1106 are fabricated on the chip package of BE 1102. BE bus 1108 provides communication among the PEs of BE 1102, namely, PE 1110, PE 1112, PE 1114, PE 1116, and these optical interfaces. Optical interface 1104 includes two ports, namely, port 1118 and port 1120, and optical interface 1106 also includes two ports, namely, port 1122 and port 1124. Ports 1118, 1120, 1122 and 1124 are connected to, respectively, optical wave guides 1126, 1128, 1130 and 1132. Optical signals are transmitted to and from BE 1102 through these optical wave guides via the ports of optical interfaces 1104 and 1106.

A plurality of BEs can be connected together in various configurations using such optical wave guides and the four optical ports of each BE. For example, as shown in FIG. 11B, two or more BEs, e.g., BE 1152, BE 1154 and BE 1156, can be connected serially through such optical ports. In this example, optical interface 1166 of BE 1152 is connected through its optical ports to the optical ports of optical interface 1160 of BE 1154. In a similar manner, the optical ports of optical interface 1162 on BE 1154 are connected to the optical ports of optical interface 1164 of BE 1156.

A matrix configuration is illustrated in FIG. 1C. In this configuration, the optical interface of each BE is connected to two other BEs. As shown in this figure, one of the optical ports of optical interface 1188 of BE 1172 is connected to an optical port of optical interface 1182 of BE 1176. The other optical port of optical interface 1188 is connected to an optical port of optical interface 1184 of BE 1178. In a similar manner, one optical port of optical interface 1190 of BE 1174 is connected to the other optical port of optical interface 1184 of BE 1178. The other optical port of optical interface 1190 is connected to an optical port of optical interface 1186 of BE 1180. This matrix configuration can be extended in a similar manner to other BEs.

Using either a serial configuration or a matrix configuration, a processor for network 104 can be constructed of any desired size and power. Of course, additional ports can be added to the optical interfaces of the BEs, or to processors having a greater or lesser number of PEs than a BE, to form other configurations.

FIG. 12A illustrates the control system and structure for the DRAM of a BE. A similar control system and structure is employed in processors having other sizes and containing more or less PEs. As shown in this figure, a cross-bar switch connects each DMAC 1210 of the four PEs comprising BE 1201 to eight bank controls 1206. Each bank control 1206 controls eight banks 1208 (only four are shown in the figure) of DRAM 1204. DRAM 1204, therefore, comprises a total of sixty-four banks. In a preferred embodiment, DRAM 1204 has a capacity of 64 megabytes, and each bank has a capacity of 1 megabyte. The smallest addressable unit within each bank, in this preferred embodiment, is a block of 1024 bits.

BE 1201 also includes switch unit 1212. Switch unit 1212 enables other APUs on BEs closely coupled to BE 1201 to access DRAM 1204. A second BE, therefore, can be closely coupled to a first BE, and each APU of each BE can address twice the number of memory locations normally accessible to an APU. The direct reading or writing of data from or to the DRAM of a first BE from or to the DRAM of a second BE can occur through a switch unit such as switch unit 1212.

For example, as shown in FIG. 12B, to accomplish such writing, the APU of a first BE, e.g., APU 1220 of BE 1222, issues a write command to a memory location of a DRAM of a second BE, e.g., DRAM 1228 of BE 1226 (rather than, as in the usual case, to DRAM 1224 of BE 1222). DMAC 1230 of BE 1222 sends the write command through cross-bar switch 1221 to bank control 1234, and bank control 1234 transmits the command to an external port 1232 connected to bank control 1234. DMAC 1238 of BE 1226 receives the write command and transfers this command to switch unit 1240 of BE 1226. Switch unit 1240 identifies the DRAM address contained in the write command and sends the data for storage in this address through bank control 1242 of BE 1226 to bank 1244 of DRAM 1228. Switch unit 1240, therefore, enables both DRAM 1224 and DRAM 1228 to function as a single memory space for the APUs of BE 1222.

FIG. 13 shows the configuration of the sixty-four banks of a DRAM. These banks are arranged into eight rows, namely, rows 1302, 1304, 1306, 1308, 1310, 1312, 1314 and 1316 and eight columns, namely, columns 1320, 1322, 1324, 1326, 1328, 1330, 1332 and 1334. Each row is controlled by a bank controller. Each bank controller, therefore, controls eight megabytes of memory.

FIGS. 14A and 14B illustrate different configurations for storing and accessing the smallest addressable memory unit of a DRAM, e.g., a block of 1024 bits. In FIG. 14A, DMAC 1402 stores in a single bank 1404 eight 1024 bit blocks 1406. In FIG. 14B, on the other hand, while DMAC 1412 reads and writes blocks of data containing 1024 bits, these blocks are interleaved between two banks, namely, bank 1414 and bank 1416. Each of these banks, therefore, contains sixteen blocks of data, and each block of data contains 512 bits. This interleaving can facilitate faster accessing of the DRAM and is useful in the processing of certain applications.

FIG. 15 illustrates the architecture for a DMAC 1504 within a PE. As illustrated in this figure, the structural hardware comprising DMAC 1506 is distributed throughout the PE such that each APU 1502 has direct access to a structural node 1504 of DMAC 1506. Each node executes the logic appropriate for memory accesses by the APU to which the node has direct access.

FIG. 16 shows an alternative embodiment of the DMAC, namely, a non-distributed architecture. In this case, the structural hardware of DMAC 1606 is centralized. APUs 1602 and PU 1604 communicate with DMAC 1606 via local PE bus 1607. DMAC 1606 is connected through a cross-bar switch to a bus 1608. Bus 1608 is connected to DRAM 1610.

As discussed above, all of the multiple APUs of a PE can independently access data in the shared DRAM. As a result, a first APU could be operating upon particular data in its local storage at a time during which a second APU requests these data. If the data were provided to the second APU at that time from the shared DRAM, the data could be invalid because of the first APU's ongoing processing which could change the data's value. If the second processor received the data from the shared DRAM at that time, therefore, the second processor could generate an erroneous result. For example, the data could be a specific value for a global variable. If the first processor changed that value during its processing, the second processor would receive an outdated value. A scheme is necessary, therefore, to synchronize the APUs' reading and writing of data from and to memory locations within the shared DRAM. This scheme must prevent the reading of data from a memory location upon which another APU currently is operating in its local storage and, therefore, which are not current, and the writing of data into a memory location storing current data.

To overcome these problems, for each addressable memory location of the DRAM, an additional segment of memory is allocated in the DRAM for storing status information relating to the data stored in the memory location. This status information includes a full/empty (F/E) bit, the identification of an APU (APU ID) requesting data from the memory location and the address of the APU's local storage (LS address) to which the requested data should be read. An addressable memory location of the DRAM can be of any size. In a preferred embodiment, this size is 1024 bits.

The setting of the F/E bit to 1 indicates that the data stored in the associated memory location are current. The setting of the F/E bit to 0, on the other hand, indicates that the data stored in the associated memory location are not current. If an APU requests the data when this bit is set to 0, the APU is prevented from immediately reading the data. In this case, an APU ID identifying the APU requesting the data, and an LS address identifying the memory location within the local storage of this APU to which the data are to be read when the data become current, are entered into the additional memory segment.

An additional memory segment also is allocated for each memory location within the local storage of the APUs. This additional memory segment stores one bit, designated the “busy bit.” The busy bit is used to reserve the associated LS memory location for the storage of specific data to be retrieved from the DRAM. If the busy bit is set to 1 for a particular memory location in local storage, the APU can use this memory location only for the writing of these specific data. On the other hand, if the busy bit is set to 0 for a particular memory location in local storage, the APU can use this memory location for the writing of any data.

Examples of the manner in which the F/E bit, the APU ID, the LS address and the busy bit are used to synchronize the reading and writing of data from and to the shared DRAM of a PE are illustrated in FIGS. 17A–17O.

As shown in FIG. 17A, one or more PEs, e.g., PE 1720, interact with DRAM 1702. PE 1720 includes APU 1722 and APU 1740. APU 1722 includes control logic 1724, and APU 1740 includes control logic 1742. APU 1722 also includes local storage 1726. This local storage includes a plurality of addressable memory locations 1728. APU 1740 includes local storage 1744, and this local storage also includes a plurality of addressable memory locations 1746. All of these addressable memory locations preferably are 1024 bits in size.

An additional segment of memory is associated with each LS addressable memory location. For example, memory segments 1729 and 1734 are associated with, respectively, local memory locations 1731 and 1732, and memory segment 1752 is associated with local memory location 1750. A “busy bit,” as discussed above, is stored in each of these additional memory segments. Local memory location 1732 is shown with several Xs to indicate that this location contains data.

DRAM 1702 contains a plurality of addressable memory locations 1704, including memory locations 1706 and 1708. These memory locations preferably also are 1024 bits in size. An additional segment of memory also is associated with each of these memory locations. For example, additional memory segment 1760 is associated with memory location 1706, and additional memory segment 1762 is associated with memory location 1708. Status information relating to the data stored in each memory location is stored in the memory segment associated with the memory location. This status information includes, as discussed above, the F/E bit, the APU ID and the LS address. For example, for memory location 1708, this status information includes F/E bit 1712, APU ID 1714 and LS address 1716.

Using the status information and the busy bit, the synchronized reading and writing of data from and to the shared DRAM among the APUs of a PE, or a group of PEs, can be achieved.

FIG. 17B illustrates the initiation of the synchronized writing of data from LS memory location 1732 of APU 1722 to memory location 1708 of DRAM 1702. Control 1724 of APU 1722 initiates the synchronized writing of these data. Since memory location 1708 is empty, F/E bit 1712 is set to 0. As a result, the data in LS location 1732 can be written into memory location 1708. If this bit were set to 1 to indicate that memory location 1708 is full and contains current, valid data, on the other hand, control 1724 would receive an error message and be prohibited from writing data into this memory location.

The result of the successful synchronized writing of the data into memory location 1708 is shown in FIG. 17C. The written data are stored in memory location 1708, and F/E bit 1712 is set to 1. This setting indicates that memory location 1708 is full and that the data in this memory location are current and valid.

FIG. 17D illustrates the initiation of the synchronized reading of data from memory location 1708 of DRAM 1702 to LS memory location 1750 of local storage 1744. To initiate this reading, the busy bit in memory segment 1752 of LS memory location 1750 is set to 1 to reserve this memory location for these data. The setting of this busy bit to 1 prevents APU 1740 from storing other data in this memory location.

As shown in FIG. 17E, control logic 1742 next issues a synchronize read command for memory location 1708 of DRAM 1702. Since F/E bit 1712 associated with this memory location is set to 1, the data stored in memory location 1708 are considered current and valid. As a result, in preparation for transferring the data from memory location 1708 to LS memory location 1750, F/E bit 1712 is set to 0. This setting is shown in FIG. 17F. The setting of this bit to 0 indicates that, following the reading of these data, the data in memory location 1708 will be invalid.

As shown in FIG. 17G, the data within memory location 1708 next are read from memory location 1708 to LS memory location 1750. FIG. 17H shows the final state. A copy of the data in memory location 1708 is stored in LS memory location 1750. F/E bit 1712 is set to 0 to indicate that the data in memory location 1708 are invalid. This invalidity is the result of alterations to these data to be made by APU 1740. The busy bit in memory segment 1752 also is set to 0. This setting indicates that LS memory location 1750 now is available to APU 1740 for any purpose, i.e., this LS memory location no longer is in a reserved state waiting for the receipt of specific data. LS memory location 1750, therefore, now can be accessed by APU 1740 for any purpose.

FIGS. 17I–17O illustrate the synchronized reading of data from a memory location of DRAM 1702, e.g., memory location 1708, to an LS memory location of an APU's local storage, e.g., LS memory location 1752 of local storage 1744, when the F/E bit for the memory location of DRAM 1702 is set to 0 to indicate that the data in this memory location are not current or valid. As shown in FIG. 17I, to initiate this transfer, the busy bit in memory segment 1752 of LS memory location 1750 is set to 1 to reserve this LS memory location for this transfer of data. As shown in FIG. 17J, control logic 1742 next issues a synchronize read command for memory location 1708 of DRAM 1702. Since the F/E bit associated with this memory location, F/E bit 1712, is set to 0, the data stored in memory location 1708 are invalid. As a result, a signal is transmitted to control logic 1742 to block the immediate reading of data from this memory location.

As shown in FIG. 17K, the APU ID 1714 and LS address 1716 for this read command next are written into memory segment 1762. In this case, the APU ID for APU 1740 and the LS memory location for LS memory location 1750 are written into memory segment 1762. When the data within memory location 1708 become current, therefore, this APU ID and LS memory location are used for determining the location to which the current data are to be transmitted.

The data in memory location 1708 become valid and current when an APU writes data into this memory location. The synchronized writing of data into memory location 1708 from, e.g., memory location 1732 of APU 1722, is illustrated in FIG. 17L. This synchronized writing of these data is permitted because F/E bit 1712 for this memory location is set to 0.

As shown in FIG. 17M, following this writing, the data in memory location 1708 become current and valid. APU ID 1714 and LS address 1716 from memory segment 1762, therefore, immediately are read from memory segment 1762, and this information then is deleted from this segment. F/E bit 1712 also is set to 0 in anticipation of the immediate reading of the data in memory location 1708. As shown in FIG. 17N, upon reading APU ID 1714 and LS address 1716, this information immediately is used for reading the valid data in memory location 1708 to LS memory location 1750 of APU 1740. The final state is shown in FIG. 170. This figure shows the valid data from memory location 1708 copied to memory location 1750, the busy bit in memory segment 1752 set to 0 and F/E bit 1712 in memory segment 1762 set to 0. The setting of this busy bit to 0 enables LS memory location 1750 now to be accessed by APU 1740 for any purpose. The setting of this F/E bit to 0 indicates that the data in memory location 1708 no longer are current and valid.

FIG. 18 summarizes the operations described above and the various states of a memory location of the DRAM based upon the states of the F/E bit, the APU ID and the LS address stored in the memory segment corresponding to the memory location. The memory location can have three states. These three states are an empty state 1880 in which the F/E bit is set to 0 and no information is provided for the APU ID or the LS address, a full state 1882 in which the F/E bit is set to 1 and no information is provided for the APU ID or LS address and a blocking state 1884 in which the F/E bit is set to 0 and information is provided for the APU ID and LS address.

As shown in this figure, in empty state 1880, a synchronized writing operation is permitted and results in a transition to full state 1882. A synchronized reading operation, however, results in a transition to the blocking state 1884 because the data in the memory location, when the memory location is in the empty state, are not current.

In full state 1882, a synchronized reading operation is permitted and results in a transition to empty state 1880. On the other hand, a synchronized writing operation in full state 1882 is prohibited to prevent overwriting of valid data. If such a writing operation is attempted in this state, no state change occurs and an error message is transmitted to the APU's corresponding control logic.

In blocking state 1884, the synchronized writing of data into the memory location is permitted and results in a transition to empty state 1880. On the other hand, a synchronized reading operation in blocking state 1884 is prohibited to prevent a conflict with the earlier synchronized reading operation which resulted in this state. If a synchronized reading operation is attempted in blocking state 1884, no state change occurs and an error message is transmitted to the APU's corresponding control logic.

The scheme described above for the synchronized reading and writing of data from and to the shared DRAM also can be used for eliminating the computational resources normally dedicated by a processor for reading data from, and writing data to, external devices. This input/output (I/O) function could be performed by a PU. However, using a modification of this synchronization scheme, an APU running an appropriate program can perform this function. For example, using this scheme, a PU receiving an interrupt request for the transmission of data from an I/O interface initiated by an external device can delegate the handling of this request to this APU. The APU then issues a synchronize write command to the I/O interface. This interface in turn signals the external device that data now can be written into the DRAM. The APU next issues a synchronize read command to the DRAM to set the DRAM's relevant memory space into a blocking state. The APU also sets to 1 the busy bits for the memory locations of the APU's local storage needed to receive the data. In the blocking state, the additional memory segments associated with the DRAM's relevant memory space contain the APU's ID and the address of the relevant memory locations of the APU's local storage. The external device next issues a synchronize write command to write the data directly to the DRAM's relevant memory space. Since this memory space is in the blocking state, the data are immediately read out of this space into the memory locations of the APU's local storage identified in the additional memory segments. The busy bits for these memory locations then are set to 0. When the external device completes writing of the data, the APU issues a signal to the PU that the transmission is complete.

Using this scheme, therefore, data transfers from external devices can be processed with minimal computational load on the PU. The APU delegated this function, however, should be able to issue an interrupt request to the PU, and the external device should have direct access to the DRAM.

The DRAM of each PE includes a plurality of “sandboxes.” A sandbox defines an area of the shared DRAM beyond which a particular APU, or set of APUs, cannot read or write data. These sandboxes provide security against the corruption of data being processed by one APU by data being processed by another APU. These sandboxes also permit the downloading of software cells from network 104 into a particular sandbox without the possibility of the software cell corrupting data throughout the DRAM. In the present invention, the sandboxes are implemented in the hardware of the DRAMs and DMACs. By implementing these sandboxes in this hardware rather than in software, advantages in speed and security are obtained.

The PU of a PE controls the sandboxes assigned to the APUs. Since the PU normally operates only trusted programs, such as an operating system, this scheme does not jeopardize security. In accordance with this scheme, the PU builds and maintains a key control table. This key control table is illustrated in FIG. 19. As shown in this figure, each entry in key control table 1902 contains an identification (ID) 1904 for an APU, an APU key 1906 for that APU and a key mask 1908. The use of this key mask is explained below. Key control table 1902 preferably is stored in a relatively fast memory, such as a static random access memory (SRAM), and is associated with the DMAC. The entries in key control table 1902 are controlled by the PU. When an APU requests the writing of data to, or the reading of data from, a particular storage location of the DRAM, the DMAC evaluates the APU key 1906 assigned to that APU in key control table 1902 against a memory access key associated with that storage location.

As shown in FIG. 20, a dedicated memory segment 2010 is assigned to each addressable storage location 2006 of a DRAM 2002. A memory access key 2012 for the storage location is stored in this dedicated memory segment. As discussed above, a further additional dedicated memory segment 2008, also associated with each addressable storage location 2006, stores synchronization information for writing data to, and reading data from, the storage location.

In operation, an APU issues a DMA command to the DMAC. This command includes the address of a storage location 2006 of DRAM 2002. Before executing this command, the DMAC looks up the requesting APU's key 1906 in key control table 1902 using the APU's ID 1904. The DMAC then compares the APU key 1906 of the requesting APU to the memory access key 2012 stored in the dedicated memory segment 2010 associated with the storage location of the DRAM to which the APU seeks access. If the two keys do not match, the DMA command is not executed. On the other hand, if the two keys match, the DMA command proceeds and the requested memory access is executed.

An alternative embodiment is illustrated in FIG. 21. In this embodiment, the PU also maintains a memory access control table 2102. Memory access control table 2102 contains an entry for each sandbox within the DRAM. In the particular example of FIG. 21, the DRAM contains 64 sandboxes. Each entry in memory access control table 2102 contains an identification (ID) 2104 for a sandbox, a base memory address 2106, a sandbox size 2108, a memory access key 2110 and an access key mask 2112. Base memory address 2106 provides the address in the DRAM, which starts a particular memory sandbox. Sandbox size 2108 provides the size of the sandbox and, therefore, the endpoint of the particular sandbox.

FIG. 22 is a flow diagram of the steps for executing a DMA command using key control table 1902 and memory access control table 2102. In step 2202, an APU issues a DMA command to the DMAC for access to a particular memory location or locations within a sandbox. This command includes a sandbox ID 2104 identifying the particular sandbox for which access is requested. In step 2204, the DMAC looks up the requesting APU's key 1906 in key control table 1902 using the APU's ID 1904. In step 2206, the DMAC uses the sandbox ID 2104 in the command to look up in memory access control table 2102 the memory access key 2110 associated with that sandbox. In step 2208, the DMAC compares the APU key 1906 assigned to the requesting APU to the access key 2110 associated with the sandbox. In step 2210, a determination is made of whether the two keys match. If the two keys do not match, the process moves to step 2212 where the DMA command does not proceed and an error message is sent to either the requesting APU, the PU or both. On the other hand, if at step 2210 the two keys are found to match, the process proceeds to step 2214 where the DMAC executes the DMA command.

The key masks for the APU keys and the memory access keys provide greater flexibility to this system. A key mask for a key converts a masked bit into a wildcard. For example, if the key mask 1908 associated with an APU key 1906 has its last two bits set to “mask,” designated by, e.g., setting these bits in key mask 1908 to 1, the APU key can be either a 1 or a 0 and still match the memory access key. For example, the APU key might be 1010. This APU key normally allows access only to a sandbox having an access key of 1010. If the APU key mask for this APU key is set to 0001, however, then this APU key can be used to gain access to sandboxes having an access key of either 1010 or 1011. Similarly, an access key 1010 with a mask set to 0001 can be accessed by an APU with an APU key of either 1010 or 1011. Since both the APU key mask and the memory key mask can be used simultaneously, numerous variations of accessibility by the APUs to the sandboxes can be established.

The present invention also provides a new programming model for the processors of system 101. This programming model employs software cells 102. These cells can be transmitted to any processor on network 104 for processing. This new programming model also utilizes the unique modular architecture of system 101 and the processors of system 101.

Software cells are processed directly by the APUs from the APU's local storage. The APUs do not directly operate on any data or programs in the DRAM. Data and programs in the DRAM are read into the APU's local storage before the APU processes these data and programs. The APU's local storage, therefore, includes a program counter, stack and other software elements for executing these programs. The PU controls the APUs by issuing direct memory access (DMA) commands to the DMAC.

The structure of software cells 102 is illustrated in FIG. 23. As shown in this figure, a software cell, e.g., software cell 2302, contains routing information section 2304 and body 2306. The information contained in routing information section 2304 is dependent upon the protocol of network 104. Routing information section 2304 contains header 2308, destination ID 2310, source ID 2312 and reply ID 2314. The destination ID includes a network address. Under the TCP/IP protocol, e.g., the network address is an Internet protocol (IP) address. Destination ID 2310 further includes the identity of the PE and APU to which the cell should be transmitted for processing. Source ID 2314 contains a network address and identifies the PE and APU from which the cell originated to enable the destination PE and APU to obtain additional information regarding the cell if necessary. Reply ID 2314 contains a network address and identifies the PE and APU to which queries regarding the cell, and the result of processing of the cell, should be directed.

Cell body 2306 contains information independent of the network's protocol. The exploded portion of FIG. 23 shows the details of cell body 2306. Header 2320 of cell body 2306 identifies the start of the cell body. Cell interface 2322 contains information necessary for the cell's utilization. This information includes global unique ID 2324, required APUs 2326, sandbox size 2328 and previous cell ID 2330.

Global unique ID 2324 uniquely identifies software cell 2302 throughout network 104. Global unique ID 2324 is generated on the basis of source ID 2312, e.g. the unique identification of a PE or APU within source ID 2312, and the time and date of generation or transmission of software cell 2302. Required APUs 2326 provides the minimum number of APUs required to execute the cell. Sandbox size 2328 provides the amount of protected memory in the required APUs' associated DRAM necessary to execute the cell. Previous cell ID 2330 provides the identity of a previous cell in a group of cells requiring sequential execution, e.g., streaming data.

Implementation section 2332 contains the cell's core information. This information includes DMA command list 2334, programs 2336 and data 2338. Programs 2336 contain the programs to be run by the APUs (called “apulets”), e.g., APU programs 2360 and 2362, and data 2338 contain the data to be processed with these programs. DMA command list 2334 contains a series of DMA commands needed to start the programs. These DMA commands include DMA commands 2340, 2350, 2355 and 2358. The PU issues these DMA commands to the DMAC.

DMA command 2340 includes VID 2342. VID 2342 is the virtual ID of an APU which is mapped to a physical ID when the DMA commands are issued. DMA command 2340 also includes load command 2344 and address 2346. Load command 2344 directs the APU to read particular information from the DRAM into local storage. Address 2346 provides the virtual address in the DRAM containing this information. The information can be, e.g., programs from programs section 2336, data from data section 2338 or other data. Finally, DMA command 2340 includes local storage address 2348. This address identifies the address in local storage where the information should be loaded. DMA commands 2350 contain similar information. Other DMA commands are also possible.

DMA command list 2334 also includes a series of kick commands, e.g., kick commands 2355 and 2358. Kick commands are commands issued by a PU to an APU to initiate the processing of a cell. DMA kick command 2355 includes virtual APU ID 2352, kick command 2354 and program counter 2356. Virtual APU ID 2352 identifies the APU to be kicked, kick command 2354 provides the relevant kick command and program counter 2356 provides the address for the program counter for executing the program. DMA kick command 2358 provides similar information for the same APU or another APU.

As noted, the PUs treat the APUs as independent processors, not co-processors. To control processing by the APUs, therefore, the PU uses commands analogous to remote procedure calls. These commands are designated “APU Remote Procedure Calls” (ARPCs). A PU implements an ARPC by issuing a series of DMA commands to the DMAC. The DMAC loads the APU program and its associated stack frame into the local storage of an APU. The PU then issues an initial kick to the APU to execute the APU Program.

FIG. 24 illustrates the steps of an ARPC for executing an apulet. The steps performed by the PU in initiating processing of the apulet by a designated APU are shown in the first portion 2402 of FIG. 24, and the steps performed by the designated APU in processing the apulet are shown in the second portion 2404 of FIG. 24.

In step 2410, the PU evaluates the apulet and then designates an APU for processing the apulet. In step 2412, the PU allocates space in the DRAM for executing the apulet by issuing a DMA command to the DMAC to set memory access keys for the necessary sandbox or sandboxes. In step 2414, the PU enables an interrupt request for the designated APU to signal completion of the apulet. In step 2418, the PU issues a DMA command to the DMAC to load the apulet from the DRAM to the local storage of the APU. In step 2420, the DMA command is executed, and the apulet is read from the DRAM to the APU's local storage. In step 2422, the PU issues a DMA command to the DMAC to load the stack frame associated with the apulet from the DRAM to the APU's local storage. In step 2423, the DMA command is executed, and the stack frame is read from the DRAM to the APU's local storage. In step 2424, the PU issues a DMA command for the DMAC to assign a key to the APU to allow the APU to read and write data from and to the hardware sandbox or sandboxes designated in step 2412. In step 2426, the DMAC updates the key control table (KTAB) with the key assigned to the APU. In step 2428, the PU issues a DMA command “kick” to the APU to start processing of the program. Other DMA commands may be issued by the PU in the execution of a particular ARPC depending upon the particular apulet.

As indicated above, second portion 2404 of FIG. 24 illustrates the steps performed by the APU in executing the apulet. In step 2430, the APU begins to execute the apulet in response to the kick command issued at step 2428. In step 2432, the APU, at the direction of the apulet, evaluates the apulet's associated stack frame. In step 2434, the APU issues multiple DMA commands to the DMAC to load data designated as needed by the stack frame from the DRAM to the APU's local storage. In step 2436, these DMA commands are executed, and the data are read from the DRAM to the APU's local storage. In step 2438, the APU executes the apulet and generates a result. In step 2440, the APU issues a DMA command to the DMAC to store the result in the DRAM. In step 2442, the DMA command is executed and the result of the apulet is written from the APU's local storage to the DRAM. In step 2444, the APU issues an interrupt request to the PU to signal that the ARPC has been completed.

The ability of APUs to perform tasks independently under the direction of a PU enables a PU to dedicate a group of APUs, and the memory resources associated with a group of APUs, to performing extended tasks. For example, a PU can dedicate one or more APUs, and a group of memory sandboxes associated with these one or more APUs, to receiving data transmitted over network 104 over an extended period and to directing the data received during this period to one or more other APUs and their associated memory sandboxes for further processing. This ability is particularly advantageous to processing streaming data transmitted over network 104, e.g., streaming MPEG or streaming ATRAC audio or video data. A PU can dedicate one or more APUs and their associated memory sandboxes to receiving these data and one or more other APUs and their associated memory sandboxes to decompressing and further processing these data. In other words, the PU can establish a dedicated pipeline relationship among a group of APUs and their associated memory sandboxes for processing such data.

In order for such processing to be performed efficiently, however, the pipeline's dedicated APUs and memory sandboxes should remain dedicated to the pipeline during periods in which processing of apulets comprising the data stream does not occur. In other words, the dedicated APUs and their associated sandboxes should be placed in a reserved state during these periods. The reservation of an APU and its associated memory sandbox or sandboxes upon completion of processing of an apulet is called a “resident termination.” A resident termination occurs in response to an instruction from a PU.

FIGS. 25, 26A and 26B illustrate the establishment of a dedicated pipeline structure comprising a group of APUs and their associated sandboxes for the processing of streaming data, e.g., streaming MPEG data. As shown in FIG. 25, the components of this pipeline structure include PE 2502 and DRAM 2518. PE 2502 includes PU 2504, DMAC 2506 and a plurality of APUs, including APU 2508, APU 2510 and APU 2512. Communications among PU 2504, DMAC 2506 and these APUs occur through PE bus 2514. Wide bandwidth bus 2516 connects DMAC 2506 to DRAM 2518. DRAM 2518 includes a plurality of sandboxes, e.g., sandbox 2520, sandbox 2522, sandbox 2524 and sandbox 2526.

FIG. 26A illustrates the steps for establishing the dedicated pipeline. In step 2610, PU 2504 assigns APU 2508 to process a network apulet. A network apulet comprises a program for processing the network protocol of network 104. In this case, this protocol is the Transmission Control Protocol/Internet Protocol (TCP/IP). TCP/IP data packets conforming to this protocol are transmitted over network 104. Upon receipt, APU 2508 processes these packets and assembles the data in the packets into software cells 102. In step 2612, PU 2504 instructs APU 2508 to perform resident terminations upon the completion of the processing of the network apulet. In step 2614, PU 2504 assigns APUs 2510 and 2512 to process MPEG apulets. In step 2615, PU 2504 instructs APUs 2510 and 2512 also to perform resident terminations upon the completion of the processing of the MPEG apulets. In step 2616, PU 2504 designates sandbox 2520 as a source sandbox for access by APU 2508 and APU 2510. In step 2618, PU 2504 designates sandbox 2522 as a destination sandbox for access by APU 2510. In step 2620, PU 2504 designates sandbox 2524 as a source sandbox for access by APU 2508 and APU 2512. In step 2622, PU 2504 designates sandbox 2526 as a destination sandbox for access by APU 2512. In step 2624, APU 2510 and APU 2512 send synchronize read commands to blocks of memory within, respectively, source sandbox 2520 and source sandbox 2524 to set these blocks of memory into the blocking state. The process finally moves to step 2628 where establishment of the dedicated pipeline is complete and the resources dedicated to the pipeline are reserved. APUs 2508, 2510 and 2512 and their associated sandboxes 2520, 2522, 2524 and 2526, therefore, enter the reserved state.

FIG. 26B illustrates the steps for processing streaming MPEG data by this dedicated pipeline. In step 2630, APU 2508, which processes the network apulet, receives in its local storage TCP/IP data packets from network 104. In step 2632, APU 2508 processes these TCP/IP data packets and assembles the data within these packets into software cells 102. In step 2634, APU 2508 examines header 2320 (FIG. 23) of the software cells to determine whether the cells contain MPEG data. If a cell does not contain MPEG data, then, in step 2636, APU 2508 transmits the cell to a general purpose sandbox designated within DRAM 2518 for processing other data by other APUs not included within the dedicated pipeline. APU 2508 also notifies PU 2504 of this transmission.

On the other hand, if a software cell contains MPEG data, then, in step 2638, APU 2508 examines previous cell ID 2330 (FIG. 23) of the cell to identify the MPEG data stream to which the cell belongs. In step 2640, APU 2508 chooses an APU of the dedicated pipeline for processing of the cell. In this case, APU 2508 chooses APU 2510 to process these data. This choice is based upon previous cell ID 2330 and load balancing factors. For example, if previous cell ID 2330 indicates that the previous software cell of the MPEG data stream to which the software cell belongs was sent to APU 2510 for processing, then the present software cell normally also will be sent to APU 2510 for processing. In step 2642, APU 2508 issues a synchronize write command to write the MPEG data to sandbox 2520. Since this sandbox previously was set to the blocking state, the MPEG data, in step 2644, automatically is read from sandbox 2520 to the local storage of APU 2510. In step 2646, APU 2510 processes the MPEG data in its local storage to generate video data. In step 2648, APU 2510 writes the video data to sandbox 2522. In step 2650, APU 2510 issues a synchronize read command to sandbox 2520 to prepare this sandbox to receive additional MPEG data. In step 2652, APU 2510 processes a resident termination. This processing causes this APU to enter the reserved state during which the APU waits to process additional MPEG data in the MPEG data stream.

Other dedicated structures can be established among a group of APUs and their associated sandboxes for processing other types of data. For example, as shown in FIG. 27, a dedicated group of APUs, e.g., APUs 2702, 2708 and 2714, can be established for performing geometric transformations upon three dimensional objects to generate two dimensional display lists. These two dimensional display lists can be further processed (rendered) by other APUs to generate pixel data. To perform this processing, sandboxes are dedicated to APUs 2702, 2708 and 2414 for storing the three dimensional objects and the display lists resulting from the processing of these objects. For example, source sandboxes 2704, 2710 and 2716 are dedicated to storing the three dimensional objects processed by, respectively, APU 2702, APU 2708 and APU 2714. In a similar manner, destination sandboxes 2706, 2712 and 2718 are dedicated to storing the display lists resulting from the processing of these three dimensional objects by, respectively, APU 2702, APU 2708 and APU 2714.

Coordinating APU 2720 is dedicated to receiving in its local storage the display lists from destination sandboxes 2706, 2712 and 2718. APU 2720 arbitrates among these display lists and sends them to other APUs for the rendering of pixel data.

The processors of system 101 also employ an absolute timer. The absolute timer provides a clock signal to the APUs and other elements of a PE which is both independent of, and faster than, the clock signal driving these elements. The use of this absolute timer is illustrated in FIG. 28.

As shown in this figure, the absolute timer establishes a time budget for the performance of tasks by the APUs. This time budget provides a time for completing these tasks which is longer than that necessary for the APUs' processing of the tasks. As a result, for each task, there is, within the time budget, a busy period and a standby period. All apulets are written for processing on the basis of this time budget regardless of the APUs' actual processing time or speed. For example, for a particular APU of a PE, a particular task may be performed during busy period 2802 of time budget 2804. Since busy period 2802 is less than time budget 2804, a standby period 2806 occurs during the time budget. During this standby period, the APU goes into a sleep mode during which less power is consumed by the APU.

The results of processing a task are not expected by other APUs, or other elements of a PE, until a time budget 2804 expires. Using the time budget established by the absolute timer, therefore, the results of the APUs' processing always are coordinated regardless of the APUs' actual processing speeds.

In the future, the speed of processing by the APUs will become faster. The time budget established by the absolute timer, however, will remain the same. For example, as shown in FIG. 28, an APU in the future will execute a task in a shorter period and, therefore, will have a longer standby period. Busy period 2808, therefore, is shorter than busy period 2802, and standby period 2810 is longer than standby period 2806. However, since programs are written for processing on the basis of the same time budget established by the absolute timer, coordination of the results of processing among the APUs is maintained. As a result, faster APUs can process programs written for slower APUs without causing conflicts in the times at which the results of this processing are expected.

In lieu of an absolute timer to establish coordination among the APUs, the PU, or one or more designated APUs, can analyze the particular instructions or microcode being executed by an APU in processing an apulet for problems in the coordination of the APUs' parallel processing created by enhanced or different operating speeds. “No operation” (“NOOP”) instructions can be inserted into the instructions and executed by some of the APUs to maintain the proper sequential completion of processing by the APUs expected by the apulet. By inserting these NOOPs into the instructions, the correct timing for the APUs' execution of all instructions can be maintained.

As described above, each processing element (PE) comprises at least one processing unit (PU) and one, or more, attached processing units (APUs) for performing parallel processing of data by one or more applications by the APUs coordinated and controlled by the PU. In this context, and turning briefly back to FIG. 18, the states of an illustrative data level synchronization (DLS) mechanism were shown for passing data back and forth between an APU and the shared memory. However, as noted earlier, this DLS mechanism can also be advantageously used to process data to, and/or from, an external device. Indeed, as will be observed from the description below, the use of DLS for I/O device handling provides other important advantages. For example, there is now the capability to hide device implementation details, the flexibility to handle multiple devices and the ability for an APU to handle streaming data from one, or multiple, external sources. Attention should now be directed to FIG. 29, which shows an illustrative DLS architecture in accordance with the inventive concept.

In FIG. 29, arrangement 2900 comprises PE 2990, DRAM (or shared memory) 2910, interface device (interface) 2915 and external device 2920. PE 2990 is representative of one or more processing elements and further comprises at least one PU 2905 and one, or more, APUs, as represented by APUs 2901, 2902 and 2903. PE 2990 is coupled to the shared memory via bus 2906 and uses the earlier-described DLS and memory protection mechanisms for writing data to, and reading data from, DRAM 2910. In accordance with the inventive concept, the DLS mechanism is now extended for use with external devices. As such, and as can be observed from FIG. 29, PE 2990 is coupled to interface 2915 via bus 2907, while DRAM 2910 is coupled, via bus 2908, to interface 2915. The latter provides coupling, via path 2916, to one or more external devices as represented by external device 2920. The external device 2920 may be one of any number of number of devices including, but not limited to memories such as a hard disk or an optical disk, processors such as an I/O processor or a graphics processor, and transceivers (such as network transceivers). Path 2916 is representative of one, or more, communication paths for coupling external device 2920 with interface 2915, e.g., packet network connections, switched network connections, a serial bus, a parallel bus, etc. Bus 2908 provides direct access by interface 2915 to DRAM 2910, as described further below.

Turning now to FIG. 30, the inventive concept will first be illustrated in the context of an external memory 3020 as the external device. In particular, each APU has associated therewith one, or more, channels for passing requests to, and/or receiving replies from, interface 2915, via bus 2907. This is illustrated in FIG. 30 for APU 2901 by channel 0 (request) (2930) and channel 1 (reply) (2935). Both elements 2930 and 2935 are illustratively one, or more, first-in-first-out (FIFO) buffers. For simplicity, other request and reply channels for the other APUs that are subsequently conveyed over bus 2907 are represented by the dashed arrows in FIG. 30. For the moment, it is assumed that only commands and status information are stored in elements 2930 and 2935. The request and reply channels exchange commands and status information with the transfer controller 2945 over bus 2907. Transfer controller 2945 is illustratively an external DMAC which processes the requests from the APUs. It can be observed from FIG. 30 that interface 2915 includes protection table 2940. This is in addition to the key control table 1902 described above with reference to FIG. 19, in the internal DMAC (not shown) of PU 2905. The use of an external protection table, such as protection table 2940, facilitates streaming of data directly from external memory 3020 to one or more sandboxes in DRAM 2910. Values for protection table 2940 are illustratively assigned by the PU in a fashion similar to that described earlier. Utilizing protection table 2940, transfer controller 2945 controls transfer path 2950 for communicating data in either direction between sandbox(es) in DRAM 2910 and external memory 3020. It should be noted that an external protection table is not required. However, if there is no external protection table, it is preferable that appropriate permissions be passed from the PU, e.g., from similarly constructed request/reply channels associated with the PU. As discussed above, the PU executes “trusted programs” and thus should be assigning the relevant read/write permissions. Further, protection table 2940 may be expanded to control accesses to external devices, or portions thereof, as represented by particular memory address regions of external memory 3020.

With continued reference to FIG. 30 and particular reference to FIGS. 31 and 32, an illustrative DLS method for use in transferring data from external memory 3020 to a local memory (not shown) of APU 2901. This method is a variation of the above-described FIG. 24, and, as such, not all steps are repeated below, or shown in FIG. 31. In this example, it is assumed that an apulet (a type of software described earlier) will be executed by APU 2901 that needs to operate on data currently stored in external memory 3020. Turning first to step 3105, of FIG. 31, PU 2905 allocates memory of DRAM 2910 for use by APU 2901. In addition, in step 3110, PU 2905 provides, via bus 2907, appropriate key protection values for the allocated memory to transfer controller 2945 of interface 2915 for use in protection table 2940 controlling access to the memory of DRAM 2915. PU 2905 does this, in addition to updating its own key control table to control access by APU 2901, in the manner described above with reference to FIG. 19. In step 3115, PU 2905 initiates execution by APU 2901 of an apulet that requires access to data currently stored in external memory 3020. Turning now to APU 2901, this APU provides, in step 3130, a request, via channel 0, to interface 2915 for the transfer of data from the external device, e.g., external memory 3020, to DRAM 2910. This request is for a synchronized writing operation to DRAM 2910 and is similar in form to the earlier-described DMA command. Illustratively, this request includes, e.g., the identification of the external device (here, external memory 3020), as well as the portion of the external device to use (here, the location of the data in external memory 3020), the amount to be transferred, the corresponding addresses in DRAM 2910, and whether the type of operation is a read or a write operation (here, a synchronized writing operation to DRAM 2910). External device information, such as the device, portion of the device to use and size information are provided, e.g., in the apulet-related information. It should also be noted that other types of external device parameters may be used including, but not limited to, device and port number, virtual channel identifiers, etc.

Turning now to FIG. 32, and with continued reference to FIG. 30, transfer controller 2945 of interface 2915 receives the transfer request from APU 2901 in step 3205. In step 3210, transfer controller 2945 checks values stored in protection table 2940 to determine if the requested memory range in DRAM 2910 is valid. If the memory range is invalid, transfer controller 2945 denies the transfer in step 3220 via channel 1. However, if the memory range is valid, transfer controller starts the transfer in step 3225 and continues transferring data (step 3230) in a DMA fashion via transfer path 2950 until finished. When the transfer is complete, transfer controller 2945 sends a transfer complete message via the reply channel in step 3235. It should be noted that if external device information is also stored in protection table 2940, transfer controller 2945 will also check, e.g., in steps 3210 and 3215, if APU 2901 has permission to use that external device before proceeding with the transfer.

In accordance with the invention, the transfer of data from external memory 3020 to APU 2901 occurs using DLS, as described above with reference to the state diagram illustrated in FIG. 18. The use of DLS in this context is illustrated in FIG. 33, which shows the data flow (as represented by the dashed arrow). Synchronized writing operations are performed by interface 2915 to DRAM 2910, while synchronized reading operations are performed by APU 2901 for reading the data from DRAM 2910 for storage in a local memory 2981. As described above with reference to FIGS. 17B to 17D, the processing of individual synchronized writing operations and synchronized reading operations by DRAM 2910 are governed by the empty, blocking, and full states of the shared memory (e.g., as represented by the values of the F/E bit, APU ID and LS address fields of the associated status information). Thus, it is possible to transfer data in an efficient manner, i.e., with low overhead, from an external device to the local memory of an APU, without requiring, e.g., that the PU first transfer the data to the DRAM for use by the APU. In other words, an I/O process that would have been performed by the PU has been pushed, in a secure and synchronized fashion, lower down into the architecture for execution by an APU. This enables an APU, e.g., in a multiple streaming application to quickly retrieve and operate on data from multiple buffers of the external memory.

It should be noted that synchronized reading operations, i.e., transfers from DRAM 2910 to an external device, e.g., external memory 3020, are also possible in a similar fashion to that described above. This is illustrated in FIG. 34, with continued reference to the flow charts of FIGS. 31 and 32. For example, in step 3115, PU 2905 initiates execution by APU 2901 of an apulet that requires transfer of data for storage in external memory 3020. As such, APU 2901 provides a request, via channel 0, to interface 2915 for the synchronized reading operation, i.e., the transfer of data from DRAM 2910 to an external device, being the external memory 3020. This request is similar in form to the earlier-described DMA command. This request includes, e.g., the identification of the external device (here, external memory 3020), the portion of the external device to use (here, the location for the data in external memory 3020), the amount to be transferred, the corresponding addresses in DRAM 2910, and whether the external device operation is a read or write operation (here, being a synchronized reading operation from DRAM 2910).

The use of DLS in this context allows interface 2915 to read data in a synchronized fashion from DRAM 2910 while APU 2901 is performing writes to DRAM 2910. This is indicated in FIG. 34, where the data flow is from a local memory 2981 of APU 2901 to the external device, as represented by the dashed arrow. In this context, the various states of DLS are represented by a value of the F/E bit and whether or not interface 2915 has attempted to read data. As such, the above-described status information for an associated memory location of DRAM 2915 is modified, as shown in FIG. 35. The status information comprises the F/E bit 3501 as described above, a device ID 3502, and an address 3503 to which the data should be transferred. The device ID 3502 identifies a type of device such as an APU or another device, such as an interface. It should be observed that in this context, since interface 2915 already includes a DMA-type controller having a protection table, the address field may not be required. That is, DRAM 2910 simply has to provide notification to interface 2915 (as identified by the device ID 3502) when a synchronized reading operation is permitted.

As noted above, the arrangement illustrated by FIG. 30 is merely illustrative and is extendible in a straightforward fashion to other types of external devices. For example, consider FIG. 36. This figure is similar to FIG. 30. As such, like numbers represent similar elements, which, as such, are not described further herein. In FIG. 36, the external device is represented by physical receiver (PHY) 3620. The latter receives packet communications from a network (not shown), e.g., an Ethernet, via path 3621, and performs decoding of the received bit stream to provide a stream of packets. In this example, the apulet executed by APU 2901 represents link layer processing of the received packet stream. That is, APU 2901 performs processing for part of a protocol stack (e.g., as protocol stack such as TCP/IP (Transmission Control Protocol/Internet Protocol)) utilizing the above-described DLS mechanism for processing data from PHY 3620.

With continued reference to FIG. 36, and turning particularly to FIG. 37, an illustrative handshaking sequence is shown to further illustrate the use of data level synchronization with an external device. In this figure, it is assumed that the respective portions of the shared memory (e.g., DRAM 2910) start in the empty state. Initially, the APU (e.g., APU 2901) sends a command via the request channel to the interface (e.g., interface 2915) requesting a synchronized writing operation from the external device to the identified portions of shared memory. Assuming that protection table checks pass interface 2915 initiates the transfer with the external device. In the meantime, the APU attempts to perform a synchronized reading operation from these portions of shared memory. Since no data has yet been written by the interface, the respective portions of the shared memory enter the blocking state. In this state, as noted earlier, the address of the local memory for the APU is stored in associated status information fields for these portions of the shared memory. Subsequently, after the interface performs the synchronized writing operation to the identified portions of the shared memory, the synchronized reading operation is executed for the APU to the addresses represented by the stored address values. As a result, these portions of the shared memory return to the empty state. Similar handshaking sequences representing the change of states (as illustrated in FIG. 18) for other permutations are straightforward and not described herein.

It should be observed that requests from one or more APUs do not have to wait for completion of each request by the interface. For example, an APU can issue multiple requests to the interface for data from one, or more, external devices. The use of DLS ensures that the data will be preserved in the shared memory until a synchronized reading operation occurs, either from the APU or from the external device (via the interface). As such, the use of DLS enables burst transfers and pipelined burst transfers to be executed between the APU and one, or more, external devices.

Another application of the inventive concept illustratively using the apparatus shown in FIG. 36 is shown in FIG. 38. APU 2901 interfaces to a number of external devices via interface 2915. These external devices are: a USB (universal serial bus) device, an IEEE 1394 (referred to commonly as “firewire”) device, a serial device, a hard disk, a network device (e.g., a network transceiver) and an optical disk. Other external devices (not shown) may include processors such as an I/O processor or a graphics processor. APU 2901 sends requests 4301 for reading data from one, or more, of these external devices. As such, each device, via the control of interface 2915, subsequently performs a synchronized writing operation to their assigned memory locations of DRAM 2910 as represented by memory locations 4311, 4312, 4313, 4314, 4315 and 4316 (each of which also illustrates the inclusion of the associated status information, which is simply represented by the F/E bit). APU 2901 retrieves the data from DRAM 2910, via bus 2906, by performing synchronized reading operations.

Attention should now be directed to FIG. 39, which illustrates another embodiment of the inventive concept. In FIG. 39, a simplified streaming arrangement 3700 is shown. Arrangement 3700 comprises PE 3790, DRAM (or shared memory) 3710, interface device (interface) 3715 and an external device, represented by physical transceiver (PHY) 3720. It should be noted that external device 3720 could also be a part of, e.g., integrated with, interface 3715. PE 3790 is representative of one or more processing elements and further comprises at least one PU 3705 and one, or more, APUs, as represented by APUs 3701, 3702 and 3703. PE 3790 is coupled to the shared memory via bus 3706 and uses the earlier-described DLS and memory protection mechanisms for writing data to, and reading data from, DRAM 3710. In accordance with the inventive concept, the DLS mechanism is now extended for use with external devices. As such, and as can be observed from FIG. 39, the APUs are coupled to interface 3715 via bus 3707. In particular, each APU has associated therewith one, or more, channels for passing requests to, and/or receiving replies from, and/or communicating data with, interface 3715, via bus 3707. This is illustrated in FIG. 39 for APU 3701 by Channel 0 (input) (3730) and Channel 1 (output) (3735). Both elements 3730 and 3735 are illustratively one, or more, first-in-first-out (FIFO) buffers. With respect to the other APUs, their input and output channels conveyed over bus 3707 are represented by the dashed arrows in FIG. 39.

Interface 3715 comprises channel interface elements 3745 and 3750, which couples the respective input and output data streams between APU 3701 and PHY 3720. The latter element is illustratively a transceiver for (a) encoding data provided from the output channel of APU 3701, via paths 3707 and 3716, for transmission over path 3721; and (b) decoding data received from path 3721 for providing decoded data to the input channel of APU 3701, via paths 3716 and 3707. Path 3721 is representative of one, or more, communication paths for coupling external device 3720 to, e.g., a packet network connection, switched network connection, a serial bus, a parallel bus, etc.

As noted above, interface 3715 includes channel interface element 3745 and 3750. Channel interface element 3745 receives the output channel from APU 3701. In accordance with the invention, the output channel itself comprises a control channel and a data channel. The control channel conveys the above-described request and reply channels, while the data channel conveys the data to be provided to the external device. In this example, the request channel conveys command information including, e.g., an external device identification (here PHY 3720) and the operation to be performed (here, a write operation). The data channel portion of the output channel represents data to be encoded by PHY 3720 for transmission via path 3721. Similarly, channel interface element 3745 is coupled to the input channel of APU 3701. The input channel itself comprises a control channel and a data channel. The control channel conveys the above-described request and reply channels, while the data channel conveys the data to be provided to the APU. In this example, the request channel conveys command information including, e.g., an external device identification (here PHY 3720) and the operation to be performed (here, a read operation). The data channel portion of the input channel represents data decoded by PHY 3720 as a result of the reception of signals received from path 3721.

It should be observed that in this illustrative embodiment a protection table is not required within interface 3715. In particular, and as described further below, each APU reads data from, or writes data to DRAM 3710, in accordance with earlier-described DLS and memory protection mechanisms as illustrated in FIG. 18.

With continued reference to FIG. 39, an illustrative method for use in transferring data from an external device to a local memory (not shown) of APU 2901 is shown in FIG. 40. This method presumes the above-described flow chart of FIG. 24 is also performed, re: assignment of protection table values by the PU, allocation of the apulet to, e.g., APU 3701, etc. In this example, the apulet executed by APU 3701 illustratively represents link layer processing of the received packet stream and for the transmitted packet stream. That is, APU 2901 performs processing for part of a protocol stack (e.g., TCP/IP) utilizing the above-described DLS mechanism.

Turning first to step 3830, of FIG. 40, APU 3701 provides a request for the transfer of data from, and to, PHY 3720, via bus 3707, to interface 3715. In this example, this request occurs via the command portions of both the input channel and the output channel. Note, however, that the use of both the input channel and the output channel is not required. This request includes, e.g., the identification of the external device (here, PHY 3720), and may also include the portion of the external device to use (e.g., a particular port), and the type of external device operation (here, a read from the external device for the input channel and a write to the external device for the output channel). It is assumed that external device information, such as the device, portion of the device to use, etc., are provided, e.g., in the apulet-related information. It should also be noted that other types of external device parameters may be used including, but not limited to, device and port number, virtual channel identifiers, etc.

In step 3805, interface 3715 receives the request and sets up the transfer to, and from, PHY 3720. It should be noted that, to the extent particular handshaking is required for PHY 3720, it is assumed this is performed by interface 3715 and is transparent to APU 3701. In step 3710, interface 3715 starts the transfer and continues transferring data from PHY 3720 until finished (step 3815). Such data transfer may, e.g., continue until a connection to a far endpoint (not shown) is torn down. This portion of the data transfer to, and from, PHY 3720 can occur synchronously or a synchronously as a function of the type of external device. The data is transferred within the data channel portion of the input channel, e.g., to a portion of the FIFO of element 3735. When the transfer is complete, interface 3715 sends a transfer complete message via the reply channels of the command portions of the input and output channels in step 3820.

In accordance with the invention, the transfer of data by APU 3701 from, and to, external device 3720 occurs using DLS, the state diagram for which is described in the foregoing with reference to FIG. 18. The use of DLS in this context is illustrated in FIG. 41. The data flow between the APU and the external device is represented by the dashed arrow. As can be observed from FIG. 41, APU 3701 receives data, via the input channel conveyed by bus 3707, directly into a local memory as described above. Similarly, APU 3701 provides data, via the output channel conveyed by bus 3707, directly from the local memory. This results in a fast, low overhead, communication channel. For example, data to be transmitted via PHY 3720 may be initially stored in DRAM 3710. APU 3701 extracts this data from DRAM 3710 using DLS via synchronized reading operations as illustrated by the corresponding dotted arrow in FIG. 41. APU 3701 then processes this data in accordance with the link layer apulet and provides the processed data, e.g., a stream of formatted packets, to PHY 3720 (via interface 3715) for further encoding for transmission. In a similar fashion, data received by PHY 3720 is decoded and provided to APU 3701 via the input channel for storage in local memory 3781 for processing by APU 3701. APU 3701 processes the data in accordance with the link layer apulet, e.g., removing headers, error checking, and provides the processed data to DRAM 3710 using DLS via synchronized writing operations, as depicted by the corresponding dotted arrow in FIG. 41.

FIG. 42 illustrates a variation of the simplified streaming arrangement shown and described above with respect to FIG. 39. Since this embodiment operates in a similar fashion to that shown in FIG. 39, not all of the figure is described in detail. Arrangement 4000, of FIG. 42, comprises PE 4090, DRAM (or shared memory) 4010, interface 4015 and an external device, represented by physical transceiver (PHY) 4020 and physical transceiver (PHY) 4080. As can be observed from FIG. 42, interface 4015 is illustratively integrated with external devices 4020 and 4080. PE 4090 is representative of one or more processing elements and further comprises at least one PU 4005 and one, or more, APUs, as represented by APUs 4001, 4002 and 4003. PE 4090 is coupled to the shared memory via bus 4006 and uses the earlier-described DLS and memory protection mechanisms for writing data to, and reading data from, DRAM 4010. As can be observed from FIG. 42, the APUs are coupled to interface 4015 via bus 4007. In particular, each APU has associated therewith one, or more, channels for passing requests to, and/or receiving replies from, and/or communicating data with, interface 4015, via bus 4007. This is illustrated in FIG. 42 for APU 4001 by input/output channel 4050 and input/output channel 4055. Both of these elements are illustratively one, or more, first-in-first-out (FIFO) buffers. Other input and output channels for the other APUs that are conveyed over bus 4007 are represented by the dashed arrows in FIG. 42.

Interface 4015 comprises elements 4030 and 4035, each of which comprises two channel interface elements 4031 and 4032, and 4036 and 4037, respectively. (These are of the type described in FIG. 39.) These elements couple the data streams to the respective external devices (here, 4020 and 4080). The external devices are illustratively transceivers for communicating data to, and from, respective paths 4021 and 4081. The external devices 4020 and/or 4080 may also include, for example, memories such as a hard disk or an optical disk, processors such as an I/O processor or a graphics processor, and transceivers (such as network transceivers).

As noted, in this example APU 4001 has access to two input/output channels (4050 and 4055) each of which further comprises the above-described input and output channel for conveying command information and data. In a similar fashion to that described above, APU 4001 executes an apulet for converting data between the external devices (4020 and 4080). Since APU 4001 has access to multiple input/output channels, it is not required that APU 4001 access DRAM 4010. As such, the variation shown in FIG. 42 provides an efficient, high-speed, arrangement for converting data between external devices.

The foregoing merely illustrates the principles of the invention and it will thus be appreciated that those skilled in the art will be able to devise numerous alternative arrangements which, although not explicitly described herein, embody the principles of the invention and are within its spirit and scope. For example, although the inventive concept has been described in the context of an input/output interface performing data level synchronization, there is no requirement that the interface perform both input and output or only be one of each type, e.g., the interface could be only an input device or only an output device or be any combination of input devices and output devices being serviced in a common input/output framework. 

1. A system comprising: an interface device operable to communicate data to and from an external device; and a memory having a plurality of memory locations each operable to store the data, at least one of the interface device and the memory being operable to store status information associated with respective ones of the memory locations, the status information including a first field and an address field, such that, for a given memory location, when a value of the first field of the associated status information equals a first value, and a value of the address field of the associated status information equals a second value, a write operation to the memory location causes data currently stored therein to be written to an address represented by the second value.
 2. The system of claim 1 wherein the address is associated with the external device.
 3. The system of claim 1 wherein the address is associated with a memory location associated with a processor in communication with the interface device.
 4. The system of claim 1 comprising a processor coupled to the memory for data access and coupled to the interface device, the processor operable to issue requests associated with the external device.
 5. The system of claim 4 wherein at least one of the requests is for reading data from the external device.
 6. The system of claim 4 wherein at least one of the requests is for writing data to the external device.
 7. The system of claim 4 wherein the memory is operable to pass the requests between the processor and the interface device.
 8. The system of claim 1 wherein the external device is integrated with the interface device.
 9. The system of claim 1 wherein the interface device communicates data between the external device and the memory using a direct memory access (DMA) transfer.
 10. A system comprising: a memory having a plurality of memory locations; a processor coupled to the memory, the processor operable to issue a request, the request having at least one of a first type and a second type; and an interface device operable to transfer data from an external device to the memory for storage therein in response to receiving a request having the first type, and to transfer data from storage in the memory to the external device in response to receiving a request having the second type, wherein memory locations of at least one of the memory and the interface device support a number of different memory states including a blocking state, such that a write operation to a given memory location in the blocking state causes data currently stored therein to be written to an address value associated with the given memory location.
 11. The system of claim 10 wherein the address value represents the external device.
 12. The system of claim 10 further comprising a local memory associated with the processor, wherein the address value represents a memory location of the local memory.
 13. The system of claim 10 wherein the first type of the request is for reading data from the external device.
 14. The system of claim 10 wherein the second type of the request is for writing data to the external device.
 15. The system of claim 10 wherein the external device is integrated with the interface device.
 16. The system of claim 10 wherein the interface device communicates data between the external device and the memory using a direct memory access (DMA) transfer.
 17. The system of claim 10 wherein the processor includes a processing unit (PU) and at least one attached processing unit (APU) , wherein the attached processing unit is operable to issue the request.
 18. The apparatus of claim 17 wherein the interface device includes a protection table for controlling access to ones of the memory locations.
 19. The apparatus of claim 18 wherein the PU initializes values of the protection table.
 20. Apparatus for interfacing between an external device and a processor, the apparatus comprising: a protection table operable to store information indicating areas of a shared memory that are accessible by the processor; a transfer controller responsive to a request from the processor to control a transfer of data between the external device and at least one of the accessible areas of the shared memory; and a transfer path operable under control by the transfer controller to transfer the data between the external device and the at least one accessible area of the shared memory, the transfer controller being operable to control the transfer the data in a synchronized manner between a memory location of the at least one accessible area and the external device according to a current memory state of the memory location, such that when the current memory state is a blocking state, a write operation to the memory location causes data currently stored in the memory location to be written to an address associated with the memory location.
 21. A method for transferring data between a processor and an external device, via an interface device, the method comprising: transferring the data between the external device and a memory local to the processor through a shared memory having a plurality of memory locations, wherein the shared memory supports a number of different memory states including a blocking state, wherein a write operation to a given memory location in the blocking state causes data currently stored therein to be written to an address value associated with the given memory location.
 22. The method of claim 21, wherein the processor is a first processor, the method further comprising sending, from a second processor, to the interface device, values for use in a protection table of the interface device, wherein the values control access to portions of the shared memory.
 23. The method of claim 21, further comprising, in the external device, receiving a command by the external device, the command requesting the data to be transferred; checking values of a protection table to determine if an address value associated with the command is valid; and if the address value is valid, performing the initiating step.
 24. The method of claim 21, wherein the associated address value represents the external device.
 25. The method of claim 21, wherein the associated address value represents a local memory associated with the processor.
 26. A device comprising: a first bus for conveying a plurality of request/reply channels, each request/reply channel associated with a processor, each request/reply channel conveying requests for communicating data between the associated processor and an external device; a second bus in data communication with a memory, for use in communicating the data using data level synchronization, the memory including a plurality of memory locations each supporting a number of different memory states including a blocking state, wherein a write operation of data to a given memory location in the blocking state causes the data currently stored in the given memory location to be written to an address value associated with the given memory location.
 27. The device of claim 26 wherein the first bus conveys values for use in a protection table, the values indicating portions of the memory that are accessible by the processor. 